Memory controller with read error handling

ABSTRACT

A method for handling a read error on a block of a memory device is disclosed. In response to a read failure indicating that at least one error handling mechanism has handled the read error on the block and fails to read data stored in the block, a memory test is trigged to be performed on the block. The memory test is configured to determine whether the block malfunctions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/352, 246, filed on Jun. 18, 2021, which is a continuation ofInternational Application No. PCT/CN2021/083886, filed on Mar. 30, 2021,entitled “MEMORY CONTROLLER WITH READ ERROR HANDLING,” the contents ofboth of which are hereby incorporated by reference in their entireties.

BACKGROUND

The present disclosure relates to memory controllers and methodsthereof.

Flash memory is a low-cost, high-density, non-volatile solid-statestorage medium that can be electrically erased and reprogrammed. Flashmemory includes an array of memory cells that can be organized intoblocks, and can be erased, written, and read block-wise. During a lifespan of Flash memory, a threshold voltage of a memory cell in a blockmay be shifted due to various factors. For example, the thresholdvoltage can be changed due to an increased usage time, a change in anexternal environment (e.g., a temperature change), and existence of amanufacturing defect, etc. A shift on the threshold voltage of thememory cell may cause a read error on the block, and data stored in theblock may be lost if the read error is unsolvable.

SUMMARY

In one aspect, a controller for controlling a memory device includes amemory and a processor. The memory is configured to store instructions.The processor is coupled to the memory and configured to execute theinstructions to perform a process including receiving data describing aread failure of a set of error handling mechanisms, where the readfailure indicates that the set of error handling mechanisms handles aread error on a block of the memory device and fails to read data storedin the block; and responsive to the read failure of the set of errorhandling mechanisms, performing a memory test on the block to determinewhether the block malfunctions.

In another aspect, a system includes a memory device and a controller.The memory device is configured to store data and includes an array ofmemory cells. The array of memory cells is organized into a plurality ofblocks. The controller is coupled to the memory device and configured tocontrol the memory device. The controller includes a memory and aprocessor. The memory is configured to store instructions. The processoris coupled to the memory and configured to execute the instructions toperform a process including receiving data describing a read failure ofa set of error handling mechanisms, where the read failure indicatesthat the set of error handling mechanisms handles a read error on ablock of the memory device and fails to read data stored in the block;and responsive to the read failure of the set of error handlingmechanisms, performing a memory test on the block to determine whetherthe block malfunctions.

In still another aspect, a method for handling a read error on a blockof a memory device is included. Data describing a read failure of a setof error handling mechanisms is received. The read failure indicatesthat the set of error handling mechanisms handles the read error on theblock and fails to read data stored in the block. Responsive to the readfailure of the set of error handling mechanisms, a memory test isperformed on the block to determine whether the block malfunctions.

According to yet another aspect, a method for handling a read error on ablock of a memory device is included. Data describing a read failure ofa set of error handling mechanisms is received. The read failureindicates that the set of error handling mechanisms handles the readerror on the block and fails to read data stored in the block.Responsive to the read failure of the set of error handling mechanisms,a memory test is performed on the block to determine whether the blockfails the memory test. Responsive to the block failing the memory test,the block is identified as a bad block.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate aspects of the present disclosure and,together with the description, further serve to explain the principlesof the present disclosure and to enable a person skilled in thepertinent art to make and use the present disclosure.

FIG. 1 illustrates a block diagram of an exemplary system having amemory controller and a memory device, according to some aspects of thepresent disclosure.

FIG. 2A illustrates a diagram of an exemplary memory card having amemory controller and a memory device, according to some aspects of thepresent disclosure.

FIG. 2B illustrates a diagram of an exemplary solid-state drive (SSD)having a memory controller and a memory device, according to someaspects of the present disclosure.

FIG. 3 illustrates a block diagram of an exemplary memory controllerinteracting with a host and a memory device, according to some aspectsof the present disclosure.

FIG. 4 illustrates a flowchart of a method for handling a read error ona block of a memory device, according to some aspects of the presentdisclosure.

FIGS. 5A-5B illustrate a flowchart of another method for handling a readerror on a block of a memory device, according to some aspects of thepresent disclosure.

The present disclosure will be described with reference to theaccompanying drawings.

DETAILED DESCRIPTION

Although specific configurations and arrangements are discussed, itshould be understood that this is done for illustrative purposes only.As such, other configurations and arrangements can be used withoutdeparting from the scope of the present disclosure. Also, the presentdisclosure can also be employed in a variety of other applications.Functional and structural features as described in the presentdisclosures can be combined, adjusted, and modified with one another andin ways not specifically depicted in the drawings, such that thesecombinations, adjustments, and modifications are within the scope of thepresent disclosure.

In general, terminology may be understood at least in part from usage incontext. For example, the term “one or more” as used herein, dependingat least in part upon context, may be used to describe any feature,structure, or characteristic in a singular sense or may be used todescribe combinations of features, structures, or characteristics in aplural sense. Similarly, terms, such as “a,” “an,” or “the,” again, maybe understood to convey a singular usage or to convey a plural usage,depending at least in part upon context. In addition, the term “basedon” may be understood as not necessarily intended to convey an exclusiveset of factors and may, instead, allow for existence of additionalfactors not necessarily expressly described, again, depending at leastin part on context.

A read error may occur to a block of a memory device (e.g., Flashmemory) due to a current leakage problem (or, a charge leakage problem)in a memory cell within the block. The current leakage problem may beincurred by a defect in the memory cell. For example, the defect canincur a current leakage from a first word line to a second word line, ora current leakage from a word line to a channel hole. Through repeaterasing and writing on the block, stress can be produced on thedefective memory cell, which may cause the current leakage problem to bemore and more serious. In some cases, the current leakage problem canincur an uncorrectable read error in a word line coupled to thedefective memory cell, such that data stored in memory cells coupled tothe word line cannot be restored. Also, a probability of a data loss onother word lines of a same redundant array of independent disks (RAID)stripe can be increased due to the current leakage problem. As a result,the integrity and reliability of data storage in the memory device areaffected.

Besides, the current leakage problem may incur a great number of readerrors on the memory device, resulting in a generation of a great numberof error codes. Each error code may trigger a series of error handlingmechanisms to be executed. For example, data stored in the memory deviceis processed using low density parity check (LDPC) codes for errorcorrection purposes. When an error code is generated to indicate a readerror on a block, a first mechanism can be implemented to handle theread error. The first mechanisms can use a default read voltage to readthe data stored in the block, and apply an LDPC hard decoding strategyfor data decoding. If the first mechanism fails to read the data storedin the block, a second mechanism can be implemented to handle the readerror on the block. The second mechanism can use a set of read voltagesin a read-retry table to read the data stored in the block, and applythe LDPC hard decoding strategy for data decoding. If the secondmechanism also fails to read the data stored in the block, a thirdmechanism can be implemented to handle the read error. The thirdmechanism can use a set of shifted read voltages to read the data storedin the block, and apply an LDPC soft decoding strategy for datadecoding. If the third mechanism also fails to read the data stored inthe block, a fourth mechanism can be implemented to use a RAID datarestoration strategy to handle the read error. If the fourth mechanismalso fails to read the data stored in the block, a data loss on theblock is reported to a host.

During implementations of the error handling mechanisms, a read delay ofthe second mechanism is higher than a page read delay, where the pageread delay represents a delay by merely reading data stored in a page inwhich the block locates. This is because the second mechanism has toiterate a read operation over all read voltage combinations (e.g., 23read voltage combinations) in the read-retry table and then apply theLDPC hard decoding strategy accordingly. A read delay of the thirdmechanism is also higher than the page read delay due to theimplementation of the LDPC soft decoding strategy. Particularly, a readdelay of the fourth mechanism is much higher than the page read delay,because all word lines within a same RAID stripe need to be read (e.g.,an entire array of memory cells within the same RAID stripe needs to beread). As a result, a frequent triggering of the error handlingmechanisms may increase a total read delay of the memory device.

Furthermore, even although the data stored in the block cannot be readsuccessfully, the above error handling mechanisms fail to identify theblock as a bad block no matter whether the failure on the block istemporary (e.g., caused by a dramatic temperature change between awriting time and a reading time) or irrecoverable (e.g., due to a moreand more severe current leakage caused by a physical defect). If thefailure on the block is irrecoverable, repeat erasing and writing on theblock may not only cause a data loss on the block repeatedly, but alsolead to an obvious decrease in the reading speed of the memory device.

To address the aforementioned issues, the present disclosure introducesa solution in which a memory test can be performed on a block with aread error to determine whether the block is malfunctioning. Forexample, when one or more error handling mechanisms fail to handle theread error on the block (e.g., failing to read data stored in theblock), the memory test can be performed on the block to determinewhether the block is a bad block. If the block has an insurmountabledefect, a failure on the block can be permanent or irrecoverable, andthe block can be labeled as a bad block. By identifying the block withthe insurmountable defect to be a bad block, the block may not be usedagain for any future data storage, so that a potential data loss on theblock can be avoided. Also, a potential triggering of the error handlingmechanisms due to read errors on the block can be prevented. A readdelay of the memory device and a potential decrease in the reading speedof the memory device caused by repeat erasing and writing on the blockcan be avoided. As a result, the reading speed of the memory device canbe enhanced, and the integrity and reliability of data storage in thememory device can be improved.

FIG. 1 illustrates a block diagram of an exemplary system 100 having amemory device and a memory controller, according to some aspects of thepresent disclosure. System 100 can be a mobile phone, a desktopcomputer, a laptop computer, a tablet, a vehicle computer, a gamingconsole, a printer, a positioning device, a wearable electronic device,a smart sensor, a virtual reality (VR) device, an argument reality (AR)device, or any other suitable electronic devices having storage therein.As shown in FIG. 1 , system 100 can include a host 108 and a memorysystem 102 having one or more memory devices 104 and a memory controller106. Host 108 can be a processor of an electronic device, such as acentral processing unit (CPU), or a system-on-chip (SoC), such as anapplication processor (AP). Host 108 can be configured to send orreceive data to or from memory devices 104.

Memory device 104 can be any memory device disclosed in the presentdisclosure. For example, memory device 104 can be a NAND Flash memorydevice or a NOR Flash memory device. In some implementations, a RAIDstructure can be implemented in memory device 104. For example, RAID 5is used in memory device 104. RAID 5 employs striping in blocks todivide the data in the blocks into a plurality of data portions,performing exclusive or (XOR) operations amongst data portions in thestripe to generate respective parity data, and stores the parity data inthe memory cells. One data portion can represent the data in one page.One stripe often includes data portions located in two-dimensions, e.g.,laterally in different blocks across different dies and differentplanes, and vertically in different levels in the same blocks. Forexample, for blocks in 4 planes and 4 dies, a stripe can include 128data portions, distributed laterally (e.g., in all the planes and dies)and vertically (e.g., in more than one level). Laterally, the stripe caninclude data portions at the same locations in different planes.Vertically, the stripe can include data portions at the same locationsat different levels. The last data portion often includes the paritydata of the stripe. In case of programming failure in one data portionof a stripe, the compromised data portion can be recovered, e.g., byperforming XOR operations, using the parity data of the stripe and therest of the data portions in the stripe. For example, for a stripe thathas 128 data portions, 127 data portions are used to store the memorydata, and one data portion is used to store the parity data of thestripe. An error correction capability of RAID 5 using such stripingconfiguration can thus be described as (127+1).

Memory controller 106 is coupled to memory device 104 and host 108 andis configured to control memory device 104, according to someimplementations. Memory controller 106 can manage the data stored inmemory device 104 and communicate with host 108. In someimplementations, memory controller 106 is designed for operating in alow duty-cycle environment like secure digital (SD) cards, compact Flash(CF) cards, universal serial bus (USB) Flash drives, or other media foruse in electronic devices, such as personal computers, digital cameras,mobile phones, etc. In some implementations, memory controller 106 isdesigned for operating in a high duty-cycle environment SSDs or embeddedmulti-media-cards (eMMCs) used as data storage for mobile devices, suchas smartphones, tablets, laptop computers, etc., and enterprise storagearrays. Memory controller 106 can be configured to control operations ofmemory device 104, such as read, erase, and program operations. Memorycontroller 106 can also be configured to manage various functions withrespect to the data stored or to be stored in memory device 104including, but not limited to, bad-block management, garbage collection,logical-to-physical address conversion, wear leveling, etc. In someimplementations, memory controller 106 is further configured to processerror correction codes (ECCs) with respect to the data read from orwritten to memory device 104. Any other suitable functions may beperformed by memory controller 106 as well, for example, formattingmemory device 104. Memory controller 106 can communicate with anexternal device (e.g., host 108) according to a particular communicationprotocol. For example, memory controller 106 may communicate with theexternal device through at least one of various interface protocols,such as a USB protocol, an MMC protocol, a peripheral componentinterconnection (PCI) protocol, a PCI-express (PCI-E) protocol, anadvanced technology attachment (ATA) protocol, a serial-ATA protocol, aparallel-ATA protocol, a small computer small interface (SCSI) protocol,an enhanced small disk interface (ESDI) protocol, an integrated driveelectronics (IDE) protocol, a Firewire protocol, etc.

In some implementations, memory controller 106 can include a processor109 and a memory 110. Processor 109 can be any suitable type ofprocessors, for example, a CPU, a microprocessor, a microcontroller unit(MCU), an SoC, or an AP, etc. Processor 109 may include variouscomputing architectures including a complex instruction set computer(CISC) architecture, a reduced instruction set computer (RISC)architecture, or an architecture implementing a combination ofinstruction sets. Although only a single processor is shown in FIG. 1 ,multiple processors may be included. Processor 109 can be configured tosend or receive data to or from memory 110. For example, processor 109can be configured to receive instructions from memory 110 and executethe instructions to provide the functionality described herein.

Memory 110 stores data (e.g., instructions or any other suitable data)that may include code or routines for performing part of or all of thetechniques described herein. Memory 110 may be a dynamic random-accessmemory (DRAM) device, a static random-access memory (SRAM) device, ahard disk drive, a flash memory device (e.g., NAND Flash memory deviceor NOR Flash memory device), or some other suitable memory device.

Memory controller 106 and one or more memory devices 104 can beintegrated into various types of storage devices, for example, beincluded in the same package, such as a universal Flash storage (UFS)package or an eMMC package. That is, memory system 102 can beimplemented and packaged into different types of end electronicproducts. In one example as shown in FIG. 2A, memory controller 106 anda single memory device 104 may be integrated into a memory card 202.Memory card 202 can include a PC card (PCMCIA, personal computer memorycard international association), a CF card, a smart media (SM) card, amemory stick, a multimedia card (MMC, RS-MMC, MMCmicro), an SD card (SD,miniSD, microSD, SDHC), a UFS, etc. Memory card 202 can further includea memory card connector 204 coupling memory card 202 with a host (e.g.,host 108 in FIG. 1 ). In another example as shown in FIG. 2B, memorycontroller 106 and multiple memory devices 104 may be integrated into anSSD 206. SSD 206 can further include an SSD connector 208 coupling SSD206 with a host (e.g., host 108 in FIG. 1 ). In some implementations,the storage capacity and/or the operation speed of SSD 206 is greaterthan those of memory card 202.

FIG. 3 illustrates a block diagram 300 of an exemplary memory controller(e.g., memory controller 106) interacting with host 108 and memorydevice 104, according to some aspects of the present disclosure. Memorydevice 104 can include a plurality of blocks for storing data receivedfrom host 108 or any other external device. Memory controller 106 can becoupled to host 108 and memory device 104. Memory controller 106 caninclude a backend 307, a transition layer 308, and a frontend 310.

Frontend 310 may be configured to handle communications between host 108and memory controller 106. Frontend 310 can include code or routinesstored in memory 110, when executed by processor 109, causing processor109 to provide the functionality described herein. In someimplementations, frontend 310 may communicate with host 108 according toa particular communication protocol. For example, frontend 310 maycommunicate with host 108 through at least one of various interfaceprotocols, such as a USB protocol, an MMC protocol, a PCI protocol, aPCI-E protocol, an ATA protocol, a serial-ATA protocol, a parallel-ATAprotocol, a SCSI protocol, an ESDI protocol, an IDE protocol, a Firewireprotocol, etc.

In some implementations, frontend 310 can receive a request from host108 and forward the request to backend 307 via transition layer 308, sothat backend 307 can fulfill the request. Examples of a request caninclude, but are not limited to, a read request to read data stored in ablock of memory device 104, a write request to erase data stored in ablock of memory device 104 and to write new data into the block, areformatting request to reformat memory device 104, or any othersuitable request. In some implementations, frontend 310 can receive datafrom backend 307 via transition layer 308, and send the data to host108.

Transition layer 308 may be configured to handle communications betweenfrontend 310 and backend 307. Transition layer 308 can act as anintermediate layer between frontend 310 and backend 307. Transitionlayer 308 can include code or routines stored in memory 110, whenexecuted by processor 109, causing processor 109 to provide thefunctionality described herein.

Backend 307 can include code or routines stored in memory 110, whenexecuted by processor 109, causing processor 109 to provide thefunctionality described herein. Backend 307 can be configured to fulfillrequests from host 108. In some implementations, backend 307 can receivea request from host 108 via frontend 310 and transition layer 308, andperform one or more operations to fulfill the request. For example,backend 307 can be configured to control operations of memory device 104(e.g., read, erase, or program operations) in response to receiving arequest from host 108 (e.g., a read request, an erasing request, or aprogramming request). Backend 307 can also be configured to managevarious functions with respect to the data stored or to be stored inmemory device 104 including, but not limited to, bad-block management,or garbage collection, etc.

In some implementations, backend 307 is further configured to processerror correction codes with respect to the data read from or written tomemory device 104. Example error correction codes can include, but arenot limited to, Hamming codes, Reed-Solomon codes, LDPC codes, etc. Forexample, backend 307 can read data from a block of memory device 104 inresponse to a read request, and process error correction codes todetermine whether data stored in the block is read successfully (e.g.,with no errors). If the data stored in the block is read successfully,backend 307 may forward the data to frontend 310 via transition layer308, so that frontend 310 can return the data to host 108. However, ifthe data stored in the block is not read successfully, backend 307 maygenerate data describing a read error on the block.

In some implementations, backend 307 can be further configured to handlethe read error on the block. For example, backend 307 can include anerror handling module 306 configured to handle the read error on theblock. Error handling module 306 can include code or routines stored inmemory 110, when executed by processor 109, causing processor 109 toprovide the functionality described herein. As described below in moredetail, error handling module 306 can be configured to implement a setof error handling mechanisms to handle the read error on the block.Responsive to the set of error handling mechanisms being able to readthe data stored in the block successfully, error handling module 306 canreturn the data to host 108. However, responsive to the set of errorhandling mechanisms also failing to read the data stored in the block,error handling module 306 may perform a memory test on the block todetermine whether the block malfunctions (e.g., whether the block is abad block). Error handling module 306 can update a mapping table ofmemory device 104 by adding a newly discovered bad block to the mappingtable. The mapping table can be used to record any bad blocks of memorydevice 104, and can be stored in memory device 104 or memory 110 ofmemory controller 106.

For example, LDPC codes can be used for error correction purposes withrespect to the data read from or written to memory device 104. As aresult, an LDPC hard decoding strategy or an LDPC soft decoding strategycan be used during a decoding process for data read from memory device104. The set of error handling mechanisms may include, but is notlimited to, one or more of the following: (1) a first mechanism thatuses a default read voltage to read the data stored in the block andapplies the LDPC hard decoding strategy for data decoding; (2) a secondmechanism that uses a set of read voltages in a read-retry table to readthe data stored in the block and applies the LDPC hard decoding strategyfor data decoding; (3) a third mechanism that uses one or more shiftedread voltages to read the data stored in the block and applies the LDPCsoft decoding strategy for data decoding; and (4) a fourth mechanismthat uses a RAID data restoration strategy to handle the read error onthe block.

In the second mechanism, the read-retry table may include various readvoltage combinations that can be applied to read data. For example, theread-retry table may include 23 read voltage combinations. Theread-retry table can be configured during the manufacture of memorycontroller 106. The second mechanism may iterate a read operation on theblock using all read voltage combinations in the read-retry table, andapply the LDPC hard decoding strategy during a decoding process for thedata retrieved from the block.

The third mechanism may use a set of shifted read voltages to read thedata stored in the block. A probability of error for each data bit canbe determined. The third mechanism may apply the LDPC soft decodingstrategy during a decoding process for the data retrieved from theblock.

In the fourth mechanism, the RAID data restoration strategy can read onall word lines within a same RAID stripe where the block locates. Forexample, the RAID data restoration strategy reads data from an entirearray of memory cells within the same RAID stripe of memory device 104.Within an error correction capability of a RAID structure, the fourthmechanism may correct read errors (if there is any) in the data based onparity data of the RAID stripe. For example, for a stripe in RAID 5 thathas 128 data portions, 127 data portions are used to store data, and 1data portion is used to store parity data of the stripe. In case of onedata portion of the stripe is compromised, the compromised data portioncan be recovered, e.g., by performing XOR operations, using the paritydata of the stripe and the rest of the data portions in the stripe.However, if there are two or more comprised data portions in the stripeof RAID 5, the two or more comprised data portions may not be recoveredusing the parity data of the stripe because it is out of the errorcorrection capability of the RAID 5 structure.

In some implementations, when a read error on a block of memory device104 is received, error handling module 306 can apply the first mechanismto handle the read error on the block and determine whether the firstmechanism reads the data stored in the block successfully. Responsive tothe first mechanism reading the data stored in the block successfully,error handling module 306 can return the data to host 108 via transitionlayer 308 and frontend 310. Or, responsive to the first mechanismfailing to read the data stored in the block, error handling module 306can generate data describing a read failure of the first mechanism, andthen apply the second mechanism to handle the read error on the block todetermine whether the second mechanism can read the data stored in theblock successfully.

Responsive to the second mechanism reading the data stored in the blocksuccessfully, error handling module 306 can return the data to host 108via transition layer 308 and frontend 310. Or, responsive to the secondmechanism also failing to read the data stored in the block, errorhandling module 306 can generate data describing a read failure of thesecond mechanism, and then apply the third mechanism to handle the readerror on the block to determine whether the third mechanism can read thedata stored in the block successfully.

Responsive to the third mechanism reading the data stored in the blocksuccessfully, error handling module 306 can return the data to host 108via transition layer 308 and frontend 310. Or, responsive to the thirdmechanism also failing to read the data stored in the block, errorhandling module 306 can generate data describing a read failure of thethird mechanism, and then apply the fourth mechanism to handle the readerror on the block to determine whether the fourth mechanism can readthe data stored in the block successfully.

Responsive to the fourth mechanism reading the data stored in the blocksuccessfully, error handling module 306 can return the data to host 108via transition layer 308 and frontend 310. Or, responsive to the fourthmechanism also failing to read the data stored in the block, errorhandling module 306 can generate data describing a read failure of thefourth mechanism, and then report a data loss on the block to host 108.

In some implementations, if one or more error handling mechanisms failto read the data stored in the block, error handling module 306 can beconfigured to perform a memory test on the block to determine whetherthe block malfunctions. For example, error handling module 306 canperform the memory test on the block if one or more of the first,second, third, and fourth mechanisms fail to read the data stored in theblock successfully. The memory test can be performed in the backgroundto minimize any impact on the performance of system 102.

In some implementations, before performing the memory test on the block,error handling module 306 may include the block in a test queue 304. Forexample, error handling module 306 may push the block to test queue 304(e.g., including an identifier of the block in test queue 304). Errorhandling module 306 may also mark the block as a temporary bad block, sothat the block may not be accessed before the memory test is performedon the block. Test queue 304 can be configured to include a set ofblocks waiting to be tested by the memory test. For example, test queue304 may include a list of identifiers of the blocks waiting to be testedby the memory test.

In some implementations, error handling module 306 may determine whetherthere is any task to be fulfilled with higher priority than the memorytest. If there is a task to be fulfilled with higher priority than thememory test, error handling module 306 may wait until the task withhigher priority is fulfilled by backend 307 and then perform the memorytest. A task to be fulfilled with higher priority than the memory testcan be, for example, a request to be fulfilled with higher priority thanthe memory test. If there is no task to be fulfilled with higherpriority than the memory test, error handling module 306 may perform thememory test based on test queue 304.

Alternatively or additionally, error handling module 306 may determinewhether there are sufficient resources available for performing thememory test (e.g., sufficient computing power, memory space, bandwidth,etc., for performing the memory test). If there are sufficient resourcesavailable for performing the memory test, error handling module 306 mayperform the memory test for one or more blocks in test queue 304.Otherwise, error handling module 306 may wait until sufficient resourcesare available for the memory test.

In some implementations, error handling module 306 may perform thememory test for each block in test queue 304 in sequence. For example, afirst block in test queue 304 is processed first, and a last block intest queue 304 is processed last (e.g., first in first out). Or, thefirst block in test queue 304 is processed last, and the last block intest queue 304 is processed first (e.g., last in first out). In someother implementations, error handling module 306 can perform the memorytest for the blocks in test queue 304 based on the total number ofvisits to each block. For example, a block that is frequently accessedby host 108 can be processed before a block that is infrequentlyaccessed by host 108.

Here, a block to be tested by the memory test may be referred to as ablock under test if no ambiguity is incurred. The memory test mayinclude a set of test routines or test procedures configured fordetermining whether a block under test is malfunctioning. For example,the memory test can be used to determine whether the block under test isa bad block (e.g., a block that has a physical defect and cannot be usedto store data any more). In some implementations, the test routines ortest procedures included in the memory test can be configured during themanufacture of memory controller 106.

Error handling module 306 may determine whether the block under testpasses the memory test. If the block fails the memory test, errorhandling module 306 can mark the block as a bad block. The block may beadded to a mapping table of memory device 104. In this case, the readerror on the block may be caused by a physical defect, and the readfailure on the block is irrecoverable or permanent. For example, duringthe memory test, error handling module 306 may apply different readvoltages with different time durations to a word line coupled to theblock, and detect an output current of each memory cell in the block todetermine whether there is any abnormality occurring to the outputcurrent. If there is an abnormality occurring to an output current of aparticular memory cell in the block (e.g., the memory cell has a seriouscurrent leakage problem), error handling module 306 may determine thatthe memory cell is damaged, and the block is marked as a bad block.

On the other hand, if the block passes the memory test, error handlingmodule 306 may identify the block as a candidate block for recyclingduring a garbage collection of memory device 104. In this case, the readfailure on the block is temporary. For example, the read failure on theblock may be caused by a dramatic temperature change between a writingtime and a reading time of the block (e.g., the block is written in anenvironment with a very low temperature and read in an environment witha very high temperature). The block can be erased and reused to storenew data. For example, error handling module 306 can release the blockfrom a list of temporary bad blocks, and push the block to a targetblock list of the garbage collection, so that the block can be recycledduring the garbage collection and reused for data storage again.

From the above description for FIG. 3 , when a read error occurs to ablock of memory device 104 and a set of error handling mechanisms alsofails to handle the read error on the block (e.g., also failing to readdata stored in the block successfully), a memory test can be performedon the block to determine whether the block is a bad block. If the blockis a bad block, the failure on the block can be permanent orirrecoverable (e.g., due to a severe current leakage caused by aphysical defect). By identifying the block with an irrecoverable failureto be a bad block, the block may not be used again for future datastorage so that a potential data loss on the block can be avoided.Additionally, a potential decrease in the reading speed of memory device104 caused by repeat erasing and writing on the block can also beavoided. As a result, the reading speed of memory device 104 can beenhanced, and the integrity and reliability of data storage in memorydevice 104 can be improved.

FIG. 4 illustrates a flowchart of a method 400 for handling a read erroron a block of memory device 104, according to some aspects of thepresent disclosure. Method 400 may be implemented by processor 109 ofmemory controller 106. It is understood that the operations shown inmethod 400 may not be exhaustive and that other operations can beperformed as well before, after, or between any of the illustratedoperations. Further, some of the operations may be performedsimultaneously, or in a different order than shown in FIG. 4 .

Referring to FIG. 4 , method 400 starts at operation 402, in which datadescribing a read failure of a set of error handling mechanisms isreceived. The read failure indicates that the set of error handlingmechanisms handles a read error on a block of memory device 104 andfails to read data stored in the block. For example, responsive toreceiving data describing the read error on the block, processor 109 mayimplement the set of error handling mechanisms to handle the read error.If the set of error handling mechanisms also fails to read the datastored in the block, processor 109 generates data describing the readfailure of the set of error handling mechanisms.

Method 400 proceeds to operation 404, as illustrated in FIG. 4 , inwhich a memory test is performed on the block to determine whether theblock malfunctions, responsive to the read failure of the set of errorhandling mechanisms. For example, processor 109 includes the block ofmemory device 104 in test queue 304. Test queue 304 is configured toinclude a set of blocks of memory device 104 waiting to be tested by thememory test. Processor 109 marks the block as a temporary bad block, sothat the block is not accessed before the memory test is performed onthe block. Next, processor 109 determines whether there is a task to befulfilled with higher priority than the memory test. If there is no taskto be fulfilled with higher priority than the memory test, processor 109proceeds to perform the memory test on the block. If the block fails thememory test, processor 109 marks the block as a bad block. On the otherhand, if the block passes the memory test, processor 109 identifies theblock as a candidate block for recycling during a garbage collection ofmemory device 104. In some implementations, processor 109 may performthe memory test for each block included in test queue 304.

FIGS. 5A-5B illustrate a flowchart of another method 500 for handling aread error on a block of memory device 104, according to some aspects ofthe present disclosure. Method 500 may be implemented by processor 109of memory controller 106. It is understood that the operations shown inmethod 500 may not be exhaustive and that other operations can beperformed as well before, after, or between any of the illustratedoperations. Further, some of the operations may be performedsimultaneously, or in a different order than shown in FIGS. 5A-5B.

Referring to FIG. 5A, method 500 starts at operation 502, in which host108 sends a read request for reading data stored in a block of memorydevice 104 to memory controller 106. Responsive to receiving the readrequest, processor 109 may perform a read operation to read data storedin the block.

Method 500 proceeds to operation 504, as illustrated in FIG. 5A, inwhich processor 109 determines whether a read error occurs to the block.If there is no read error on the block (e.g., the data stored in theblock is read successfully with no errors), method 500 proceeds tooperation 506. Otherwise, method 500 proceeds to operation 508.

At operation 506, the data stored in the block is returned to host 108.For example, processor 109 returns the data to host 108.

At operation 508, a first mechanism is applied to handle the read error.The first mechanism uses a default read voltage and an LDPC harddecoding strategy. For example, processor 109 is configured to apply thefirst mechanism to handle the read error.

Method 500 proceeds to operation 510, as illustrated in FIG. 5A, inwhich processor 109 determines whether a read failure occurs to thefirst mechanism. If the read failure occurs to the first mechanism,method 500 proceeds to operation 512. Otherwise, method 500 proceeds tooperation 506.

At operation 512, a second mechanism is applied to handle the readerror. The second mechanism uses a set of read voltages in a read-retrytable and the LDPC hard decoding strategy. For example, processor 109 isconfigured to apply the second mechanism to handle the read error.

Method 500 proceeds to operation 514, as illustrated in FIG. 5A, inwhich processor 109 determines whether a read failure occurs to thesecond mechanism. If the read failure occurs to the second mechanism,method 500 proceeds to operation 516. Otherwise, method 500 proceeds tooperation 506.

At operation 516, a third mechanism is applied to handle the read error.The third mechanism uses a shifted read voltage and an LDPC softdecoding strategy. For example, processor 109 is configured to apply thethird mechanism to handle the read error.

Method 500 proceeds to operation 518, as illustrated in FIG. 5A, inwhich processor 109 determines whether a read failure occurs to thethird mechanism. If the read failure occurs to the third mechanism,method 500 proceeds to operation 520. Otherwise, method 500 proceeds tooperation 506.

At operation 520, a fourth mechanism is applied to handle the readerror. The fourth mechanism uses a RAID data restoration strategy torecover data stored in the block. For example, processor 109 isconfigured to apply the fourth mechanism to handle the read error.

Method 500 proceeds to operation 522, as illustrated in FIG. 5A, inwhich processor 109 determines whether a read failure occurs to thefourth mechanism. If the read failure occurs to the fourth mechanism,method 500 proceeds to operation 524. Otherwise, method 500 proceeds tooperation 506.

At operation 524, a data loss on the block is reported to host 108. Forexample, processor 109 reports the data loss on the block to host 108.

With reference to FIG. 5A, operations illustrated in FIG. 5B can beperformed before operation 512 if the read failure occurs to the firstmechanism. Alternatively, operations illustrated in FIG. 5B can beperformed before operation 516 if the read failure also occurs to thesecond mechanism. Alternatively, operations illustrated in FIG. 5B canbe performed before operation 520 if the read failure also occurs to thethird mechanism. Alternatively, operations illustrated in FIG. 5B can beperformed after operation 522 (before or after operation 524) if theread failure also occurs to the fourth mechanism.

Referring to FIG. 5B, method 500 proceeds to operation 526, in which theblock is included in a test queue. The test queue is configured toinclude a set of blocks waiting to be tested by a memory test. Forexample, processor 109 pushes the block to the test queue.

Method 500 proceeds to operation 528, as illustrated in FIG. 5B, inwhich the block is marked as a temporary bad block, so that the block isnot accessed before the memory test is performed on the block. Forexample, processor 109 marks the block as a temporary bad block.

Method 500 proceeds to operation 530, as illustrated in FIG. 5B, inwhich processor 109 determines whether there is a task to be fulfilledwith higher priority than the memory test. If there is a task having ahigher priority than the memory test, method 500 proceeds to operation532. Otherwise, method 500 proceeds to operation 534.

At operation 532, the task with higher priority than the memory test isperformed. For example, processor 109 performs the task, and thenreturns to operation 530.

At operation 534, the memory test is performed on the block to determinewhether the block malfunctions. For example, processor 109 performs thememory test on the block to determine whether the block is a bad block.In some implementations, processor 109 may perform the memory test oneach block in the test queue, so that each block in the test queue canbe determined whether it is malfunctioning (e.g., operations 534, 536,538, and 540 can be performed for each block in the test queue).

Method 500 proceeds to operation 536, as illustrated in FIG. 5B, inwhich processor 109 determines whether the block fails the memory test.If the block fails the memory test, method 500 proceeds to operation538. Otherwise, method 500 proceeds to operation 540.

At operation 538, the block is marked as a bad block that has a physicaldefect. For example, processor 109 identifies the block as a bad blockand updates a mapping table to include the block.

At operation 540, the block is identified as a candidate block forrecycling during a garbage collection of memory device 104. For example,processor 109 releases the block from a list of temporary bad blocks,and pushes the block to a target block list of the garbage collection,so that the block can be recycled during the garbage collection andreused for data storage again.

According to one aspect of the present disclosure, a controller forcontrolling a memory device includes a memory and a processor coupled tothe memory. The memory is configured to store instructions. Theprocessor is configured to execute the instructions to perform a processincluding receiving data describing a read failure of a set of errorhandling mechanisms, where the read failure indicates that the set oferror handling mechanisms handles a read error on a block of the memorydevice and fails to read data stored in the block; and responsive to theread failure of the set of error handling mechanisms, performing amemory test on the block to determine whether the block malfunctions.

In some implementations, the processor is configured to execute theinstructions to perform the process further, including: including theblock of the memory device in a test queue, where the test queue isconfigured to include a set of blocks of the memory device waiting to betested by the memory test; and marking the block of the memory device asa temporary bad block, so that the block is not accessed before thememory test is performed on the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including determiningwhether there is a task to be fulfilled with higher priority than thememory test, where the memory test on the block is performed responsiveto there is no task to be fulfilled with higher priority than the memorytest.

In some implementations, to perform the memory test on the block todetermine whether the block malfunctions, the processor is configured toexecute the instructions to perform the process further includingresponsive to determining that the block fails the memory test, markingthe block as a bad block that has a physical defect; or responsive todetermining that the block passes the memory test, identifying the blockas a candidate block for recycling during a garbage collection of thememory device.

In some implementations, the processor is configured to execute theinstructions to perform the process further including receiving datadescribing the read error on the block; applying the set of errorhandling mechanisms to handle the read error on the block to determinewhether the set of error handling mechanisms reads the data stored inthe block successfully; and responsive to the set of error handlingmechanisms failing to read the data stored in the block, generating thedata describing the read failure of the set of error handlingmechanisms.

In some implementations, to apply the set of error handling mechanismsto handle the read error on the block, the processor is configured toexecute the instructions to perform the process further including:applying a first mechanism to handle the read error on the block todetermine whether the first mechanism reads the data stored in the blocksuccessfully, where the first mechanism uses a default read voltage toread the data stored in the block and applies a LDPC hard decodingstrategy for data decoding; responsive to the first mechanism failing toread the data stored in the block, applying a second mechanism to handlethe read error on the block to determine whether the second mechanismreads the data stored in the block successfully, where the secondmechanism uses a set of read voltages in a read-retry table to read thedata stored in the block and applies the LDPC hard decoding strategy fordata decoding; and responsive to the second mechanism failing to readthe data stored in the block, applying a third mechanism to handle theread error on the block to determine whether the third mechanism readsthe data stored in the block successfully, where the third mechanismuses a shifted read voltage to read the data stored in the block andapplies a LDPC soft decoding strategy for data decoding.

In some implementations, to generate the data describing the readfailure of the set of error handling mechanisms, the processor isconfigured to execute the instructions to perform the process furtherincluding responsive to the third mechanism failing to read the datastored in the block, generating the data describing the read failure toindicate that each of the first mechanism, the second mechanism, and thethird mechanism fails to read the data stored in the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including responsive to thethird mechanism failing to read the data stored in the block, applying afourth mechanism to handle the read error on the block to determinewhether the fourth mechanism reads the data stored in the blocksuccessfully, where the fourth mechanism uses a RAID data restorationstrategy to handle the read error on the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including responsive to thefourth mechanism failing to read the data stored in the block, reportinga data loss on the block to a host; or responsive to the fourthmechanism reading the data stored in the block successfully, returningthe data stored in the block to the host.

According to another aspect of the present disclosure, a system includesa memory device and a controller. The memory device is configured tostore data and includes an array of memory cells. The array of memorycells is organized into a plurality of blocks. The controller is coupledto the memory device and configured to control the memory device. Thecontroller includes a memory and a processor. The memory is configuredto store instructions. The processor is coupled to the memory andconfigured to execute the instructions to perform a process includingreceiving data describing a read failure of a set of error handlingmechanisms, where the read failure indicates that the set of errorhandling mechanisms handles a read error on a block of the memory deviceand fails to read data stored in the block; and responsive to the readfailure of the set of error handling mechanisms, performing a memorytest on the block to determine whether the block malfunctions.

In some implementations, the system further includes a host coupled tothe memory controller and configured to send or receive the data storedin the memory device.

In some implementations, the processor is configured to execute theinstructions to perform the process further including the block of thememory device in a test queue, where the test queue is configured toinclude a set of blocks of the memory device waiting to be tested by thememory test; and marking the block of the memory device as a temporarybad block, so that the block is not accessed before the memory test isperformed on the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including determiningwhether there is a task to be fulfilled with higher priority than thememory test, where the memory test on the block is performed responsiveto there is no task to be fulfilled with higher priority than the memorytest.

In some implementations, to perform the memory test on the block todetermine whether the block malfunctions, the processor is configured toexecute the instructions to perform the process further includingresponsive to determining that the block fails the memory test, markingthe block as a bad block that has a physical defect; or responsive todetermining that the block passes the memory test, identifying the blockas a candidate block for recycling during a garbage collection of thememory device.

In some implementations, the processor is configured to execute theinstructions to perform the process further including receiving datadescribing the read error on the block; applying the set of errorhandling mechanisms to handle the read error on the block to determinewhether the set of error handling mechanisms reads the data stored inthe block successfully; and responsive to the set of error handlingmechanisms failing to read the data stored in the block, generating thedata describing the read failure of the set of error handlingmechanisms.

In some implementations, to apply the set of error handling mechanismsto handle the read error on the block, the processor is configured toexecute the instructions to perform the process further including:applying a first mechanism to handle the read error on the block todetermine whether the first mechanism reads the data stored in the blocksuccessfully, where the first mechanism uses a default read voltage toread the data stored in the block and applies a LDPC hard decodingstrategy for data decoding; responsive to the first mechanism failing toread the data stored in the block, applying a second mechanism to handlethe read error on the block to determine whether the second mechanismreads the data stored in the block successfully, where the secondmechanism uses a set of read voltages in a read-retry table to read thedata stored in the block and applies the LDPC hard decoding strategy fordata decoding; and responsive to the second mechanism failing to readthe data stored in the block, applying a third mechanism to handle theread error on the block to determine whether the third mechanism readsthe data stored in the block successfully, where the third mechanismuses a shifted read voltage to read the data stored in the block andapplies a LDPC soft decoding strategy for data decoding.

In some implementations, to generate the data describing the readfailure of the set of error handling mechanisms, the processor isconfigured to execute the instructions to perform the process furtherincluding responsive to the third mechanism failing to read the datastored in the block, generating the data describing the read failure toindicate that each of the first mechanism, the second mechanism, and thethird mechanism fails to read the data stored in the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including responsive to thethird mechanism failing to read the data stored in the block, applying afourth mechanism to handle the read error on the block to determinewhether the fourth mechanism reads the data stored in the blocksuccessfully, where the fourth mechanism uses a RAID data restorationstrategy to handle the read error on the block.

In some implementations, the processor is configured to execute theinstructions to perform the process further including responsive to thefourth mechanism failing to read the data stored in the block, reportinga data loss on the block to a host; or responsive to the fourthmechanism reading the data stored in the block successfully, returningthe data stored in the block to the host.

According to still another aspect of the present disclosure, a methodfor handling a read error on a block of a memory device is included.Data describing a read failure of a set of error handling mechanisms isreceived. The read failure indicates that the set of error handlingmechanisms handles the read error on the block and fails to read datastored in the block. Responsive to the read failure of the set of errorhandling mechanisms, a memory test is performed on the block todetermine whether the block malfunctions.

In some implementations, the block of the memory device is included in atest queue. The test queue is configured to include a set of blocks ofthe memory device waiting to be tested by the memory test. The block ofthe memory device is marked as a temporary bad block, so that the blockis not accessed before the memory test is performed on the block.

In some implementations, it is determined whether there is a task to befulfilled with higher priority than the memory test. The memory test onthe block is performed responsive to there is no task to be fulfilledwith higher priority than the memory test.

In some implementations, performing the memory test on the block todetermine whether the block malfunctions include responsive todetermining that the block fails the memory test, marking the block as abad block that has a physical defect; or responsive to determining thatthe block passes the memory test, identifying the block as a candidateblock for recycling during a garbage collection of the memory device.

In some implementations, data describing the read error on the block isreceived. The set of error handling mechanisms is applied to handle theread error on the block to determine whether the set of error handlingmechanisms reads the data stored in the block successfully. Responsiveto the set of error handling mechanisms failing to read the data storedin the block, the data describing the read failure of the set of errorhandling mechanisms is generated.

In some implementations, applying the set of error handling mechanismsto handle the read error on the block to determine whether the set oferror handling mechanisms reads the data stored in the blocksuccessfully includes: applying a first mechanism to handle the readerror on the block to determine whether the first mechanism reads thedata stored in the block successfully, where the first mechanism uses adefault read voltage to read the data stored in the block and applies aLDPC hard decoding strategy for data decoding; responsive to the firstmechanism failing to read the data stored in the block, applying asecond mechanism to handle the read error on the block to determinewhether the second mechanism reads the data stored in the blocksuccessfully, where the second mechanism uses a set of read voltages ina read-retry table to read the data stored in the block and applies theLDPC hard decoding strategy for data decoding; and responsive to thesecond mechanism failing to read the data stored in the block, applyinga third mechanism to handle the read error on the block to determinewhether the third mechanism reads the data stored in the blocksuccessfully, where the third mechanism uses a shifted read voltage toread the data stored in the block and applies a LDPC soft decodingstrategy for data decoding.

In some implementations, generating the data describing the read failureof the set of error handling mechanisms includes responsive to the thirdmechanism failing to read the data stored in the block, generating thedata describing the read failure to indicate that each of the firstmechanism, the second mechanism, and the third mechanism fails to readthe data stored in the block.

In some implementations, responsive to the third mechanism failing toread the data stored in the block, a fourth mechanism is applied tohandle the read error on the block to determine whether the fourthmechanism reads the data stored in the block successfully, where thefourth mechanism uses a RAID data restoration strategy to handle theread error on the block.

In some implementations, responsive to the fourth mechanism failing toread the data stored in the block, a data loss on the block is reportedto a host; or responsive to the fourth mechanism reading the data storedin the block successfully, the data stored in the block is returned tothe host.

According to yet another aspect of the present disclosure, a method forhandling a read error on a block of a memory device is included. Datadescribing a read failure of a set of error handling mechanisms isreceived. The read failure indicates that the set of error handlingmechanisms handles the read error on the block and fails to read datastored in the block. Responsive to the read failure of the set of errorhandling mechanisms, a memory test is performed on the block todetermine whether the block fails the memory test. Responsive to theblock failing the memory test, the block is identified as a bad block.

In some implementations, the block of the memory device is included in atest queue. The test queue is configured to include a set of blocks ofthe memory device waiting to be tested by the memory test. The block ofthe memory device is marked as a temporary bad block, so that the blockis not accessed before the memory test is performed on the block.

In some implementations, it is determined whether there is a task to befulfilled with higher priority than the memory test. The memory test onthe block is performed responsive to there being no task to be fulfilledwith higher priority than the memory test.

In some implementations, data describing the read error on the block isreceived. The set of error handling mechanisms is applied to handle theread error on the block to determine whether the set of error handlingmechanisms reads the data stored in the block successfully. Responsiveto the set of error handling mechanisms failing to read the data storedin the block, the data describing the read failure of the set of errorhandling mechanisms is generated.

In some implementations, applying the set of error handling mechanismsto handle the read error on the block to determine whether the set oferror handling mechanisms reads the data stored in the blocksuccessfully includes: applying a first mechanism to handle the readerror on the block to determine whether the first mechanism reads thedata stored in the block successfully, where the first mechanism uses adefault read voltage to read the data stored in the block and applies aLDPC hard decoding strategy for data decoding; responsive to the firstmechanism failing to read the data stored in the block, applying asecond mechanism to handle the read error on the block to determinewhether the second mechanism reads the data stored in the blocksuccessfully, where the second mechanism uses a set of read voltages ina read-retry table to read the data stored in the block and applies theLDPC hard decoding strategy for data decoding; and responsive to thesecond mechanism failing to read the data stored in the block, applyinga third mechanism to handle the read error on the block to determinewhether the third mechanism reads the data stored in the blocksuccessfully, where the third mechanism uses a shifted read voltage toread the data stored in the block and applies an LDPC soft decodingstrategy for data decoding.

In some implementations, generating the data describing the read failureof the set of error handling mechanisms includes responsive to the thirdmechanism failing to read the data stored in the block, generating thedata describing the read failure to indicate that each of the firstmechanism, the second mechanism, and the third mechanism fails to readthe data stored in the block.

In some implementations, responsive to the third mechanism failing toread the data stored in the block, a fourth mechanism is applied tohandle the read error on the block to determine whether the fourthmechanism reads the data stored in the block successfully. The fourthmechanism uses a RAID data restoration strategy to handle the read erroron the block.

In some implementations, responsive to the fourth mechanism failing toread the data stored in the block, a data loss on the block to a host isreported.

The foregoing description of the specific implementations can be readilymodified and/or adapted for various applications. Therefore, suchadaptations and modifications are intended to be within the meaning andrange of equivalents of the disclosed implementations, based on theteaching and guidance presented herein.

The breadth and scope of the present disclosure should not be limited byany of the above-described exemplary implementations, but should bedefined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for handling a read error on a block ofa memory device, comprising: in response to a read failure indicatingthat at least one error handling mechanism has handled the read error onthe block and fails to read data stored in the block, triggering toperform a memory test on the block, the memory test being configured todetermine whether the block malfunctions.
 2. The method of claim 1,wherein the memory test comprises a set of test procedures configured toapply a plurality of read voltages to evaluate whether the block is abad block.
 3. The method of claim 1, wherein performing the memory testcomprises: applying a plurality of read voltages to a word line coupledto the block; and detecting, at least in part, an output current of eachmemory cell in the block to determine whether there is any abnormalityoccurring to the output current, thereby determining whether the blockmalfunctions.
 4. The method of claim 1, further comprising: in responseto determining that the block passes the memory test: releasing theblock from a list of temporary bad blocks, the temporal bad blocks beingconfigured as inaccessible, at least, before performing the memory teston the block; and pushing the block to a target block list of a garbagecollection to identify the block as a candidate block for recycling. 5.The method of claim 1, further comprising: in response to determiningthat the block fails the memory test: updating a mapping table toinclude the block that fails the memory test to identify the block as abad block.
 6. The method of claim 1, further comprising: beforeperforming the memory test on the block: pushing the block to a testqueue that is configured to include a set of blocks of the memory devicewaiting for the memory test; and pushing the block to a list oftemporary bad blocks, the temporal bad blocks being configured asinaccessible, at least, before performing the memory test on the block.7. The method of claim 6, further comprising: in response to determiningthat there is a task to be fulfilled with higher priority than thememory test: performing the task before performing the memory test onthe block.
 8. The method of claim 1, further comprising: applying the atleast one error handling mechanism to handle the read error on theblock; and in response to the at least one error handling mechanismfailing to read the data stored in the block, generating notificationdata indicative of the read failure of the at least one error handlingmechanism on reading the data stored in the block.
 9. The method ofclaim 1, wherein the read failure of the at least one error handlingmechanism comprises one of: a first read failure indicating that a firsterror handling mechanism failed on handling the read error on the block,the first error handling mechanism being configured to use a defaultread voltage to read the data stored in the block and a low densityparity check (LDPC) hard decoding strategy for data decoding; a secondread failure indicating that the first error handling mechanism and asecond error handling mechanism failed on handling the read error on theblock, the second error handling mechanism configured to use a set ofread voltages in a read-retry table to read the data stored in the blockand the LDPC hard decoding strategy for the data decoding; a third readfailure indicating that the first error handling mechanism, the seconderror handling mechanism, and a third error handling mechanism failed onhandling the read error on the block, the third error handling mechanismbeing configured to use a set of shifted read voltages to read the datastored in the block and an LDPC soft decoding strategy for the datadecoding; or a fourth read failure indicating that the first errorhandling mechanism, the second error handling mechanism, the third errorhandling mechanism, and a fourth error handling mechanism failed onhandling the read error on the block, the fourth error handlingmechanism being configured to use a redundant array of independent disks(RAID) data restoration strategy to handle the read error on the block.10. A system, comprising: a memory device comprising an array of memorycells that comprises a plurality of blocks configured for storing data;and a controller coupled to the memory device and configured to: inresponse to a read failure indicating that at least one error handlingmechanism has handled a read error on one block of the plurality ofblocks and fails to read the data stored in the block, trigger toperform a memory test on the block, the memory test being configured todetermine whether the block malfunctions.
 11. The system of claim 10,wherein the memory test comprises a set of test procedures configured toapply a plurality of read voltages to evaluate whether the block is abad block.
 12. The system of claim 10, wherein the controller is furtherconfigured to: apply a plurality of read voltages to a word line coupledto the block; and control to detect, at least in part, an output currentof each memory cell in the block to determine whether there is anyabnormality occurring to the output current, thereby determining whetherthe block malfunctions.
 13. The system of claim 10, wherein thecontroller is further configured to: in response to determining that theblock passes the memory test: release the block from a list of temporarybad blocks, the temporal bad blocks being configured as inaccessible, atleast, before performing the memory test on the block; and push theblock to a target block list of a garbage collection to identify theblock as a candidate block for recycling.
 14. The system of claim 10,wherein the controller is further configured to: in response todetermining that the block fails the memory test: update a mapping tableto include the block that fails the memory test to identify the block asa bad block.
 15. The system of claim 10, wherein: the controllercomprises a test queue configured to include a set of blocks of thememory device waiting for the memory test; and before performing thememory test on the block, the controller is further configured to: pushthe block to the test queue; and push the block to a list of temporarybad blocks, the temporal bad blocks being configured as inaccessible, atleast, before performing the memory test on the block.
 16. The system ofclaim 15, wherein in response to determining that there is a task to befulfilled with higher priority than the memory test, the controller isfurther configured to: perform the task before performing the memorytest on the block.
 17. The system of claim 10, wherein the controller isconfigured to: apply the at least one error handling mechanism to handlethe read error on the block; and in response to the at least one errorhandling mechanism failing to read the data stored in the block,generate notification data indicative of the read failure of the atleast one error handling mechanism on reading the data stored in theblock.
 18. The system of claim 10, wherein the read failure of the atleast one error handling mechanism comprises one of: a first readfailure indicating that a first error handling mechanism failed onhandling the read error on the block, the first error handling mechanismbeing configured to use a default read voltage to read the data storedin the block and a low density parity check (LDPC) hard decodingstrategy for data decoding; a second read failure indicating that thefirst error handling mechanism and a second error handling mechanismfailed on handling the read error on the block, the second errorhandling mechanism configured to use a set of read voltages in aread-retry table to read the data stored in the block and the LDPC harddecoding strategy for the data decoding; a third read failure indicatingthat the first error handling mechanism, the second error handlingmechanism, and a third error handling mechanism failed on handling theread error on the block, the third error handling mechanism beingconfigured to use a set of shifted read voltages to read the data storedin the block and an LDPC soft decoding strategy for the data decoding;or a fourth read failure indicating that the first error handlingmechanism, the second error handling mechanism, the third error handlingmechanism, and a fourth error handling mechanism failed on handling theread error on the block, the fourth error handling mechanism beingconfigured to use a redundant array of independent disks (RAID) datarestoration strategy to handle the read error on the block.
 19. Thesystem of claim 10, further comprising: a host configured to send a readrequest, for reading the data stored in the block, to the memory devicethrough the controller, wherein the controller is further configured to:in response to the at least one error handling mechanism reading thedata stored in the block successfully, return the data to the host; andin response to the read failure indicating that at least one errorhandling mechanism failing to read the data stored in the block, reporta data loss to the host.
 20. A non-transitory storage medium, coupled toa processor and storing instructions that, when executed by theprocessor, cause the processor to: in response to a read failureindicating that at least one error handling mechanism has handled a readerror on a block of a memory device and failed to read data stored inthe block, trigger to perform a memory test on the block, the memorytest being configured to determine whether the block malfunctions.